Methods and systems for communication management

ABSTRACT

Methods and systems for communication management are disclosed. Services and/or clients in a system can specify or determine timeout parameters in communication requests. A timeout parameter can be a time allocated to process a request and/or fulfill a task associated with a request. Tasks can be delegated to other devices or services, and the tasks can be sent with additional timeout parameters based on the first timeout parameter. A notification can be sent when a time to process a request or fulfill a task is predicted to exceed one or more of the timeout parameters.

BACKGROUND

Current network transactions have time restrictions. Networkcommunications requests, such as HTTP requests, can be terminated if thetime needed to process the request is beyond a predefined timeoutparameter. The termination can leave communication requestors unsure ofwhether terminated network transactions actually went through. These andother shortcomings are addressed in the present disclosure.

SUMMARY

It is to be understood that both the following summary and the followingdetailed description are exemplary and explanatory only and are notrestrictive, as claimed. Provided are methods and systems forcommunication management. Services and/or clients in a system canspecify or determine timeout parameters in communication requests. Atimeout parameter can be a time allocated to process a request and/orfulfill a task associated with a request. A notification can be sentwhen time to process a request or fulfill a task is predicted to exceeda respective timeout parameter.

In an aspect, when a client transmits a request to a service, or whenone service transmits a request to another service, the client or theservice that transmits the request can specify a timeout parameter inthe request. The service that receives the request can determine atimeout parameter associated with the request. For example, the timeoutparameter can comprise a time limit to complete a task. The service thatreceives the request can identify a first task based on the task in therequest and associate a second timeout parameter with the first task.For example, the service that receives the request can subtract anoverhead time from the first timeout parameter to derive a secondtimeout parameter. In an aspect, the service that receives the requestcan delegate one or more other services to process the first task. Forexample, the one or more other services can complete one or moreportions of the first task. Each of the one or more other services canbe allocated a respective timeout parameter (e.g., a third timeoutparameter, a fourth timeout parameter, etc.). A notification can be sentif one or more timeout parameters (e.g., first timeout parameter, secondtimeout parameter, third timeout parameter, fourth timeout parameter)are predicted to be exceeded. The notification can be sent to the clientor the service that initiates the request.

An example method can comprise receiving a first request at a firstdevice. A first timeout parameter associated with the first request canbe determined. A first task can be identified based on the firstrequest. A second timeout parameter can be associated with the firsttask based on the first timeout parameter and the first task. The secondtimeout parameter can be processed based on the second timeoutparameter.

Another example method can comprise receiving a first request and afirst timeout parameter associated with the first request. A timeallocation for processing a first portion of the first request can bedetermined. A second timeout parameter can be determined by subtractingat least the time allocation from the first timeout parameter. A secondrequest to perform a second portion of the first request can be sent. Inan aspect, the second request can be sent with the second timeoutparameter.

Another example method can comprise sending a first request with a firsttimeout parameter from a first device to a second device and receiving,at the first device, from the second device, a notification indicating atimeout prediction. The second device can be configured to send thenotification before the first timeout parameter is exceeded. A secondtimeout parameter can be determined, at the first device, in response toreceiving the notification, and a second request comprising the secondtimeout parameter can be sent.

Additional advantages will be set forth in part in the description whichfollows or may be learned by practice. The advantages will be realizedand attained by means of the elements and combinations particularlypointed out in the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate embodiments and together with thedescription, serve to explain the principles of the methods and systems:

FIG. 1 is a block diagram of an exemplary system;

FIG. 2 is a block diagram of an exemplary system in which the presentmethods and systems can operate;

FIG. 3 is a flowchart illustrating an example method;

FIG. 4 is a flowchart illustrating another example method;

FIG. 5 is a flowchart illustrating yet another example method; and

FIG. 6 is a block diagram illustrating an example computing device inwhich the present methods and systems can operate.

DETAILED DESCRIPTION

Before the present methods and systems are disclosed and described, itis to be understood that the methods and systems are not limited tospecific methods, specific components, or to particular implementations.It is also to be understood that the terminology used herein is for thepurpose of describing particular embodiments only and is not intended tobe limiting.

As used in the specification and the appended claims, the singular forms“a,” “an,” and “the” include plural referents unless the context clearlydictates otherwise. Ranges may be expressed herein as from “about” oneparticular value, and/or to “about” another particular value. When sucha range is expressed, another embodiment includes from the oneparticular value and/or to the other particular value. Similarly, whenvalues are expressed as approximations, by use of the antecedent“about,” it will be understood that the particular value forms anotherembodiment. It will be further understood that the endpoints of each ofthe ranges are significant both in relation to the other endpoint, andindependently of the other endpoint.

“Optional” or “optionally” means that the subsequently described eventor circumstance may or may not occur, and that the description includesinstances where said event or circumstance occurs and instances where itdoes not.

Throughout the description and claims of this specification, the word“comprise” and variations of the word, such as “comprising” and“comprises,” means “including but not limited to,” and is not intendedto exclude, for example, other components, integers or steps.“Exemplary” means “an example of” and is not intended to convey anindication of a preferred or ideal embodiment. “Such as” is not used ina restrictive sense, but for explanatory purposes.

Disclosed are components that can be used to perform the disclosedmethods and systems. These and other components are disclosed herein,and it is understood that when combinations, subsets, interactions,groups, etc. of these components are disclosed that while specificreference of each various individual and collective combinations andpermutation of these may not be explicitly disclosed, each isspecifically contemplated and described herein, for all methods andsystems. This applies to all aspects of this application including, butnot limited to, steps in disclosed methods. Thus, if there are a varietyof additional steps that can be performed it is understood that each ofthese additional steps can be performed with any specific embodiment orcombination of embodiments of the disclosed methods.

The present methods and systems may be understood more readily byreference to the following detailed description of preferred embodimentsand the examples included therein and to the Figures and their previousand following description.

As will be appreciated by one skilled in the art, the methods andsystems may take the form of an entirely hardware embodiment, anentirely software embodiment, or an embodiment combining software andhardware aspects. Furthermore, the methods and systems may take the formof a computer program product on a computer-readable storage mediumhaving computer-readable program instructions (e.g., computer software)embodied in the storage medium. More particularly, the present methodsand systems may take the form of web-implemented computer software. Anysuitable computer-readable storage medium may be utilized including harddisks, CD-ROMs, optical storage devices, or magnetic storage devices.

Embodiments of the methods and systems are described below withreference to block diagrams and flowchart illustrations of methods,systems, apparatuses and computer program products. It will beunderstood that each block of the block diagrams and flowchartillustrations, and combinations of blocks in the block diagrams andflowchart illustrations, respectively, can be implemented by computerprogram instructions. These computer program instructions may be loadedto a general purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions which execute on the computer or other programmabledata processing apparatus create a means for implementing the functionsspecified in the flowchart block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including computer-readableinstructions for implementing the function specified in the flowchartblock or blocks. The computer program instructions may also be loaded toa computer or other programmable data processing apparatus to cause aseries of operational steps to be performed on the computer or otherprogrammable apparatus to produce a computer-implemented process suchthat the instructions that execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

Accordingly, blocks of the block diagrams and flowchart illustrationssupport combinations of means for performing the specified functions,combinations of steps for performing the specified functions and programinstruction means for performing the specified functions. It will alsobe understood that each block of the block diagrams and flowchartillustrations, and combinations of blocks in the block diagrams andflowchart illustrations, can be implemented by special purposehardware-based computer systems that perform the specified functions orsteps, or combinations of special purpose hardware and computerinstructions.

Methods and systems for communication management are disclosed. Servicesand/or clients in a system can specify or determine one or more timeoutparameters in communication requests. A timeout parameter can comprisean amount of time allocated to process a request and/or otherwisefulfill a task associated with a request. A notification can be providedwhen time to process a request or fulfill a task is predicted to exceeda respective timeout parameter. As an example, when a client transmits arequest to a service, or when one service transmits a request to anotherservice, the client or the service that transmits the request canspecify a timeout parameter in the request. The service that receivesthe request can determine a timeout parameter associated with therequest. For example, the timeout parameter can comprise a time limit tocomplete a task. The service that receives the request can identify afirst task based on the task in the request and associate a secondtimeout parameter with the first task. For example, the service thatreceives the request can subtract an overhead time from the firsttimeout parameter to derive a second timeout parameter. In an aspect,the service that receives the request can delegate one or more otherservices to process the first task. For example, the one or more otherservices can complete one or more portions of the first task. Each ofthe one or more other services can be allocated a respective timeoutparameter (e.g., a third timeout parameter, a fourth timeout parameter).A notification can be sent if one or more timeout parameters (e.g.,second timeout parameter, third timeout parameter, fourth timeoutparameter) are predicted to be exceeded. The notification can be sent tothe client or the service that initiates the request.

As another example, the provided methods and system can comprise aclient informing a service (e.g., device running a service) of a timelimit (e.g., 30 seconds) to complete a transaction. The service can usethe time limit to make a time allocation. For example, the service candetermine a plurality of time limits for a plurality of sub serviceproviders to complete a transaction. The time allocation can be based onone or more service level agreements (SLAs) and subtracting an overheadfactor. For example, if Service A was given 30 seconds to respond, theservice A can allocate service B 25 seconds to respond. The 5 seconddifference allows time for network overhead as well as internalprocessing. If service A uses two services, service A can give 15seconds to service B and 10 seconds to service D if service B normallytakes longer to respond than service D. The time allocation can beadjusted. For example, if service A was given 20 seconds to respond,service A can adjust time limits for service B and service Daccordingly.

FIG. 1 illustrates a block diagram of an example system forcommunication management. In an aspect, the system can comprise one ormore clients (e.g., client 102) and/or one or more services (e.g.,service 104 a, service 104 b, service 104 c, service 104 d). As anexample, the one or more clients (e.g., client 102) can comprise acomputer, a telephone, a smartphone, a mobile device, a laptop, atablet, a set top box, a PDA, a network device, a server, and the like.In an aspect, a service can comprise a local or remote process, thread,service, server, application, and/or the like. As an example, a servicecan comprise network (e.g., Internet) connectivity services, mediamanagement (e.g., media server) services, content services (e.g., videogaming), content streaming services, broadband services, data routingservices, telephone services, electronic commerce services, electronicfunds transfer services, online transaction processing services,electronic data interchange services, or other network-related services.As an example, a service can be implemented and/or provided, at least inpart, by a personal computer, a portable computer, a smartphone, aserver, a router, a network device, a peer device, a switch, othercommon network node, and the like.

In an aspect, the one or more services and/or clients can be configuredto communicate by one or more communication links with other localand/or remote services, such as data, devices, and files. In an aspect,a communication link between the one or more clients (e.g., client 102)and one or more services (e.g., service 104 a, service 104 b, service104 c, service 104 d) or between two services can comprise a privateand/or public network, such as the Internet, a local area (LAN) network,metropolitan area network (MAN), a wide area network (WAN) and the like.The communication link can comprise wireless links (e.g., radiofrequency, satellite) and/or physical links (e.g., fiber optic cable,coaxial cable, Ethernet cable). In an aspect, the one or more clients(e.g., client 102) and one or more services (e.g., service 104 a,service 104 b, service 104 c, service 104 d) can be implemented asseparate network entities or reside in a common location. For example,the communication link can comprise a local network, computer bus,computer interconnect, and/or the like. One or more services and/orclients can be implemented as network topology, such as tree, star,mesh, bus, line, ring, and the like.

The disclosed methods can be implemented in a public switched telephonenetwork (PSTN) system, a public land mobile network (PLMN) system, awireless distribution system, a wired or cable distribution system, acoaxial cable distribution system, an ultra-high frequency (UHF) or veryhigh frequency (VHF) radio frequency system, a satellite or otherextra-terrestrial system, a cellular distribution system, a power-linebroadcast system, a fiber optic network, or any combinations of thesesystems and/or networks.

In one aspect, the one or more services can be configured to processrequests from other services and/or clients. For example, the one ormore services can be configured to determine one or more tasks based ona request. For example, the tasks can be configured to process,complete, and/or otherwise fulfill the request. In one aspect, the oneor more services can be configured to delegate and/or otherwise providethe tasks to other services. As an example, a request can compriserequesting a content item in a specific format. As another example, arequest can comprise coding or decoding a content item. As anotherexample, a request can comprise routing a data block to a particulardestination. As another example, a request can comprise processing anelectronic commerce transaction. As another example, a request cancomprise a digital rights management (DRM) license request. As anotherexample, a request can comprise a travel scheduling request for hotel,flight, car rental, and the like. As another example, a request cancomprise a user interface request to a multi-tier presentation service(e.g., Player Service). As another example, a request can comprise amultiplayer video game request.

In one aspect, the one or more services can be configured to determineone or more timeout parameters associated with requests, tasks, and/orthe like. A timeout parameter can indicate the maximum allowed time forthe interaction between a request initiator and a request receiver. Inan aspect, one or more timeout parameters can be determined based on thetype of service associated with requests, type of tasks associated withrequests, number of services needed to process requests, properties ofnetwork connections (e.g., high bandwidth, low bandwidth, high latency,low latency), and other factors. In an aspect, one or more mathematicaloperations can be used to determine a timeout parameter (e.g.,subtractions, additions, predetermined mathematical formulas). In anaspect, one or more timeout parameter can be determined based on arequest processing history. For example, a request processing historycan comprise a record of past network transactions. A record in arequest processing history can comprise information on the type of aparticular transaction and/or service, whether the particulartransaction was successful, how long to complete the particulartransaction, clients and services involved in the particulartransaction, load on the participant clients and services during thetransaction, network conditions (e.g., bandwidth, latency), networktraffic during the particular transaction, and or the like. The service104 a can determine a first timeout parameter (e.g., 30 seconds) uponreceiving a first request from the client 102.

In an aspect, one or more services can receive one or more timeoutparameters from other services or one or more clients. As an example,the service 104 a can receive a first request from the client 102. Theclient 102 can specify a first timeout parameter (e.g., 30 seconds) inthe first request. In an aspect, upon receiving the first request (e.g.,a request to complete a transaction in 30 seconds), the service 104 acan identify a first task based on the first request. As an example,identifying the first task can comprise identifying one or more tasks tocomplete the first request. Additionally, one or more other services(e.g., service 104 b, service 104 c) can be identified to complete thetransaction indicated in the first request. For example, certainservices can be identified with pre-defined tasks and/or categories oftasks. For example, the service 104 a can associate a second timeoutparameter (e.g., 25 seconds) with the first task based on the firsttimeout parameter (e.g., 30 seconds) and the first task. In an aspect,the service 104 a can subtract a network overhead time from the firsttimeout parameter to derive the second timeout parameter. In anotheraspect, the service 104 a can determine the second timeout parameterbased on an expected time to accomplish the task (e.g., or a portionthereof, or a subtask), backlog of the identified service, priority ofthe first task, and/or the like. The service 104 a can provide thesecond timeout parameter (e.g., 25 seconds) with a second request to theservice 104 b to process the first task. For example, the second timeoutparameter can be determined by subtracting a time value (e.g., 5seconds) from the first timeout parameter. As an example, the time valuecan be an expected time delay associated with overhead of processing thefirst request (e.g., by the service 104 a).

In an aspect, the first task can be processed. The first task can beconfigured to fulfill a first portion of the first request. For example,service 104 b can process the first task according to the second timeoutparameter (e.g., 25 seconds). In an aspect, in response to the firsttask exceeding the second timeout parameter, a notification indicativeof the first request exceeding the first timeout parameter can be sentto the client 102. In an aspect, the notification can be sent before thefirst timeout parameter is exceeded. As an example, the notification canbe a sound, a code, text, a message, or the like. In an aspect, thenotification can be sent in the form of a custom HTTP header or field ina header.

In an aspect, the methods can further comprise identifying a second taskbased on at least one of the first task and the first request andassociating a third timeout parameter with the second task. For example,a second task can be processed by the service 104 c and the thirdtimeout parameter (e.g., 10 seconds) can be associated with the secondtask. A third request can be sent to service 104 c. The third requestcan comprise a request to process the second task based on the thirdtimeout parameter. In an aspect, in response to the second taskexceeding the third timeout parameter, a notification indicative ofexceeding at least one of the first timeout parameter and the secondtimeout parameter can be sent to the client 102. In an aspect, thenotification can be sent before the first timeout parameter is exceededand/or the second timeout parameter is exceeded. For example, anotification can be sent (e.g., from the service 104 c) to one or moreother services, such as service 104 b and service 104 a that the thirdtimeout parameter is exceeded or predicted to be exceeded. In response,service 104 b can send a notification that the second timeout parameteris exceeded or predicted to be exceeded. Service 104 a can send anotification that the first timeout parameter is exceeded or predictedto be exceeded to the client 102.

In an aspect, the disclosed methods can be used in any combination ofcomponents of FIG. 1. For example, the methods can be used only betweenthe client 102 and the service 104 a. In another aspect, any componentof FIG. 1 can transmit a request to any other component of FIG. 1. Forexample, the client 102 can transmit a first request to the service 104a, and the service 104 a can call one or more other services to processthe first request (e.g., complete a task). For example, the service 104a can transmit a second request to the service 104 b. As anotherexample, the client 102 can transmit a request to the 104 b directly. Inturn, the service 104 b can transmit one or more requests to a pluralityof other services (not shown) and allocate each of the plurality ofother services a respective amount of time to complete their respectivetasks. If the one or more requests to the plurality of other servicesare issued in parallel, the time allocated to each of the plurality ofother services can be a same number (e.g., 25 second). If the one ormore requests to the plurality of other services are issuedsequentially, then the service 104 b can determine time allocation tothe plurality of other services, such that total allocated time to theplurality of other services can be less than a certain number (e.g., 25seconds).

FIG. 2 illustrates various aspects of an example system 200 forcommunication management. In one aspect, the system 200 can comprise aplurality of devices, for example, a first device 202, a second device204 a, a third device 204 b, and the fourth device 204 c. As an example,the plurality of devices can comprise electronic devices such ascomputers, smartphones, laptops, tablets, set top boxes, displaydevices, servers, network devices, and the like. The plurality ofdevices (e.g., first device 204, second device 204 a, third device 204b, fourth device 204 c) can be implemented as separate network entitiesor reside in a common location. The plurality of devices can communicatevia network 205. The network 205 can comprise a private and/or publicnetwork, such as the Internet or a local area network. Other forms ofcommunications can be used such as wired and wireless telecommunicationchannels.

In one aspect, the network 205 can comprise a packet switched network(e.g., internet protocol based network), a non-packet switched network(e.g., quadrature amplitude modulation based network), and/or the like.The network 205 can comprise network adapters, switches, routers,modems, and the like connected through wireless links (e.g., radiofrequency, satellite) and/or physical links (e.g., fiber optic cable,coaxial cable, Ethernet cable, or a combination thereof). In one aspect,the network 205 can be configured to provide communication fromtelephone, cellular, modem, and/or other electronic devices to andthroughout the system 200.

As an example, the first device 202 can be configured as a client. In anaspect, the first device 202 can comprise a communication element 206for providing an interface to a user to interact with the first device202 and/or one or more of the plurality of devices (e.g., second device204 a, third device 204 b). The communication element 206 can be anyinterface for presenting and/or receiving information to/from a user. Anexample interface may be communication interface such as a web browser(e.g., Internet Explorer, Mozilla Firefox, Google Chrome, Safari, or thelike). As another example, the communication element 206 can request orquery various files from a local source and/or a remote source. As afurther example, the communication element 206 can transmit data to alocal or remote device (e.g., second device 204 a, third device 204 b).As an example, the communication element can 206 can be used to transmita request for a service (e.g., content streaming service) to one or moreof the plurality of devices (e.g., second device 204 a).

In an aspect, the first device 202 can be associated with a useridentifier or device identifier 208. As an example, the deviceidentifier 208 can be any identifier, token, character, string, or thelike, for differentiating one user or device (e.g., first device 202)from another user or device. In a further aspect, the device identifier208 can identify a user or user device as belonging to a particularclass of users or user devices. As a further example, the deviceidentifier 208 can comprise information relating to the user device suchas a manufacturer, a model or type of device, a service providerassociated with the first device 202, a state of the first device 202, alocator, and/or a label or classifier. Other information can berepresented by the device identifier 208.

In an aspect, the first device 202 can be associated with a serviceelement 210. As an example, the service element 210 can comprise anidentification of a service provider associated with the first device202 and/or with the class of first device 202. The class of the firstdevice 202 can be related to a type of device, capability of device,type of service being provided, and/or a level of service (e.g.,business class, service tier, service package, etc.). As an example, theservice element 210 can comprise information relating to or provided bya communication service provider (e.g., content provider) that isproviding or enabling data flow such as communication services to thefirst device 202. As a further example, the service element 210 cancomprise information relating to a preferred service provider for one ormore particular services relating to the first device 202. Otherinformation can be represented by the service element 210. As anexample, service element 210 can be used to determine a service providerfor a particular service request.

In an aspect, the second device 204 a, the third device 204 b, and thefourth device 204 c can be configured as servers. As an example, thesecond device 204 a and the third device 204 b can communicate with thefirst device 202 for providing data and/or services. As an example, thesecond device 204 a and/or the third device 204 b can provide servicessuch media management services, content services, streaming services,coding/decoding services, electronic commerce services, or othernetwork-related services. In an aspect, the second device 204 a canallow the first device 202 to interact with remote resources such asdata, devices, and files, for example, the fourth device 204 c.

In an aspect, the second device 204 a, the third device 204 b, and thefourth device 204 c can each comprise a respective request processingelement. For example, the second device 204 a can be associated with arequest processing element 212. As an example, the request processingelement 212 can process a request from another device or networkcomponent, for example, first device 202, third device 204 b, and/or thefourth device 204 c. In an aspect, the request processing element 212can determine one or more tasks associated with a received request(e.g., a request received from the first device 202). In another aspect,the request processing element 212 can identify one or more services toprocess one or more portions of a received request. In another aspect,the request processing element 212 can determine one or more timeoutparameters associated with requests and/or tasks.

In an aspect, one or more of the second device 204 a, the third device204 b, and the fourth device 204 c can be associated with one or morerequest processing history databases, such a request processing history214. The request processing history databases can be used to determineone or more timeout parameters associated with requests and/or tasks.For example, the second device 204 a can be associated with a requestprocessing history 214. In an aspect, the request processing history 214can allow the use of historical information to determine, estimate,and/or otherwise predict appropriate values for timeout parameters. Forexample, a request and/or task can be compared to historical informationin the request processing history 214 to determine an appropriate amountof time for a timeout parameter. In an aspect, a request processinghistory 214 can comprise a record of past network transactions. A recordin the request processing history 214 can represent a particular requestand/or transaction. For example, the request can comprise information onthe type of a transaction and/or a service (e.g., content service,coding service, electronic commerce service, gaming service), whether aparticular transaction was successful, how long to complete a particulartransaction, clients and services involved in a particular transaction,load on involved clients and services during a particular transaction,network condition (e.g., bandwidth, latency) and network traffic duringa particular transaction, and/or the like.

FIG. 3 is a flowchart illustrating an example 300 method. At step 302, afirst request can be received (e.g., by a first device, service 104 a).The first request can comprise a request to initiate a transaction(e.g., network transaction). The request can be received from a service,a client, a device, or another component in the network. A service cancomprise a local or remote process, thread, service, server,application, and/or the like. For example, a service provider (e.g.,first device, service 104 a) can receive a first request from a client(e.g., client 102). In an aspect, the first request can comprise arequest for a service and an identity of the service requestor (e.g.,device identifier 108). As an example, the first request can comprise arequest for a content service, a streaming service, a mobile commerceservice, an electronic funds transfer service, an Internet marketingservice, an online transaction processing service, an electronic datainterchange service, and/or the like.

At step 304, a first timeout parameter associated with the first requestcan be determined (e.g., by a first device, service 104 a). A timeoutparameter can indicate the maximum allowed time for the interactionbetween the first request initiator (e.g., client 102) and the firstrequest receiver (e.g., first device, service 104 a). In an aspect, thefirst request can comprise a first timeout parameter (e.g., 30 seconds).In another aspect, the first timeout parameter can be determined at thefirst request receiver (e.g., first device, service 104 a) uponreceiving the first request. In an aspect, the first timeout parametercan be determined based on the type of requested service, whether one ormore other services are needed to process the first request, propertiesof network connections (e.g., high bandwidth, low bandwidth, highlatency, low latency) associated with the first request initiator andone or more first request processors, and other factors. In an aspect,the service 104 a and/or first device can determine the first timeoutparameter based on a request processing history. For example, a requestprocessing history can comprise a record of past network transactions.In an aspect, a record in the request processing history can represent aparticular request and/or transaction. A record can comprise informationon the type of a particular transaction and/or service, whether theparticular transaction was successful, how long to complete theparticular transaction, clients and services involved in the particulartransaction, load on the participant clients and services during thetransaction, network conditions (e.g., bandwidth, latency) and networktraffic during the particular transaction, and or the like.

At step 306, a first task can be identified (e.g., by a first device,service 104 a) based on the first request. In an aspect, the serviceand/or device that receives the first request can identify a first taskbased on the first request. For example, service 104 a and/or the firstdevice can identify a first task and determine that a second service(e.g., service 104 b) and/or second device can perform the first task.In an aspect, the first task can be configured to fulfill a firstportion of the first request. In the scenario of content streamingservice, the first task can comprise encoding requested content streamsand encapsulating the encoded content in a format suitable for delivery.

At step 308, a second timeout parameter can be associated with the firsttask based on the first timeout parameter and the first task (e.g., by afirst device, service 104 a). In an aspect, when the service 104 aand/or first device identifies the first task, the service 104 a and/orfirst device can associate a second timeout parameter (e.g., 25 seconds)with the first task based on the first timeout parameter (e.g., 30seconds) and the first task. In an aspect, the second timeout parametercan be determined by one or more predefined formula (e.g., addition,subtraction, multiplication, division, and other mathematicaloperations) and/or by comparison to historical information. As aspecific example, the second timeout parameter can be determined bysubtracting a time value (e.g., 5 seconds) from the first timeoutparameter. As an example, the time value can be an expected time delayassociated with overhead of processing the first request. For example,the time delay can comprise time delay in transmitting the firstrequest. As another example, the time delay can comprise identifying oneor more services to process the first task. As another example, the timedelay can comprise determining current network conditions such asbandwidth, latency, loads, and/or the like. As another example, the timecan comprise accessing a request processing history.

At step 310, the first task can be processed based on the second timeoutparameter. Processing the first task can comprise fulfilling the firsttask, for example, by performing a calculation, retrieving information,converting data, sending data, and/or the like. For example, the firsttask can be performed at the first device, such as by a service runningon the first device. As another example, the first task can be processedat another device, such as a second device. Processing the first taskcan comprise sending the second timeout parameter with a second requestto process the first task. The first device (e.g., service 104 a) cansend the second timeout parameter (e.g., 25 seconds) with a secondrequest to the second device or to a service (e.g., first service)running on the first device to process the first task. The first deviceand/or second device can process the first task according to the secondtimeout parameter (e.g., 25 seconds). In an aspect, in response to thefirst task exceeding or a prediction of exceeding the second timeoutparameter, a notification indicative of the first request exceeding orbeing predicted to exceed the first timeout parameter can be sent. Forexample, the notification can be sent by the first device and/or seconddevice to the client (e.g., client 102), device (e.g., first device),and/or service that sent the first request. In an aspect, thenotification can be sent before the first timeout parameter is exceeded.The notification can be transmitted to the client, device, and/orservice before the connection between the client 102 and the deviceand/or service 104 a is terminated. As an example, the notification canbe a sound, a code, text, a message, or the like. In an aspect, thenotification can be sent in the form of a custom HTTP header or field ina header.

In an aspect, a second task can be identified based on at least one ofthe first task and the first request. In the scenario of contentstreaming service, the first task can comprise encoding requestedcontent streams and encapsulating the encoded content in a formatsuitable for delivery. In an aspect, the second task can compriseidentifying coding format suitable for a content requestor (e.g., client102). In another aspect, the second task can comprise distributing theencapsulated content the content requestor (e.g., client 102).

A third timeout parameter can be associated with the second task. In anaspect, the first device, second device (e.g., service 104 b), and/or aservice running on the first device or second device can determine athird timeout parameter (e.g., 10 seconds) associated with theidentified second task. In another aspect, the service and/or devicethat processes the second task (e.g., the service 104 c) can determine athird timeout parameter (e.g., 10 seconds) associated with the secondtask.

It can be determined whether the second task exceeded the third timeoutparameter. In an aspect, the service (e.g., service 104 c) and/or device(e.g., first device, second device, third device) that processes thesecond task can determine that processing the second task would (e.g.,is predicted to) exceed the third timeout parameter (e.g., 10 seconds).In an aspect, the determination can be made based on one or more of theprogress of processing the second task, the time elapsed to process thesecond task, current network conditions, current load on the serviceand/or device that processes the second task (e.g., service 104 c), andthe like. In another aspect, the determination can be made by comparingthe current transaction with one or more similar transactions in arequest processing history.

A notification indicative of exceeding at least one of the first timeoutparameter and the second timeout parameter can be sent in response tothe second task exceeding the third timeout parameter. For example, inresponse to the second task exceeding or being predicted to exceed thethird timeout parameter (e.g., 10 seconds), a notification indicative ofexceeding or being predicted to exceed at least one of the first timeoutparameter and the second timeout parameter can be sent. For example, anotification that the second task exceeds or is predicted to exceed thethird timeout parameter can be determined by the service 104 c and/orthird device and transmitted to service 104 b and/or second device. Inturn, the service 104 b and/or second device can send a notificationindicative of exceeding the second timeout parameter and transmit thenotification to service 104 a and/or first device. The service 104 a cansend a notification to the client 102 indicative of exceeding or thefirst timeout parameter. As an example, the notification can be a sound,a code, text, a message, or the like. The notification indicative ofexceeding or being predicted to exceed at least one of the first timeoutparameter and the second timeout parameter can be sent in the form of acustom HTTP header or field in a header.

FIG. 4 is a flowchart illustrating an example method 400. At step 402, afirst request and a first timeout parameter associated with the firstrequest can be received. The first request can comprise a request tocomplete a task or initiate a transaction (e.g., network transaction).The request can be received from a service, a client, or anothercomponent in the network. A service can comprise a local or remoteprocess, thread, service, server, application, and/or the like. Forexample, the first request can comprise a first timeout parameter. As anexample, the first timeout parameter can be 3 seconds, 5 seconds, 20seconds, 30 seconds or any value appropriate for a particularapplication. In an aspect, the first timeout parameter can be apredefined timeout parameter, or a timeout parameter dynamicallydetermined when the first request is initiated. For example, the firsttimeout parameter can be determined by the type of service associatedwith the first request, current network conditions associated with thefirst request initiator and/or first requestor receiver, processinghistory related to the type of service, and/or the like.

In an aspect, the first request can be and/or comprise a request toperform a subtask of a third request. For example, the client 102 canreceive a third request from another client or a service. The client 102can determine a subtask of the task and a timeout parameter associatedwith the subtask. The client 102 can transmit the first request to aservice (e.g., 104 b) or another client to perform the determinedsubtask. In an aspect, the first timeout parameter can be based on athird timeout parameter associated with the third request. For example,if the third timeout parameter associated with the third requestspecifies 40 seconds to process the third request, the client 102 canallocate 30 seconds as the first timeout parameter to the process thesubtask of the third request. The first timeout parameter can betransmitted along with the first request.

At step 404, a time allocation for processing a first portion of thefirst request can be determined. As an example, if the time allocationto process the first request is 30 seconds, the time allocation forprocessing a first portion of the first request can be 20 seconds. In anaspect, the time allocation for processing a first portion of the firstrequest can be determined based on, the services (e.g., 104 a, 104 b,104 c) that participate in the processing the first portion of the firstrequest, the number of services, hardware performance of the services(e.g., CPU speed, hardware load, memory, etc.) that participate in theprocessing the first portion of the first request, type of serviceassociated with the first request (e.g., content service, electronicfunds transfer, web service, etc.), type of network connection (e.g.,bandwidth, latency, etc.) associated with the first request, currentnetwork traffic (e.g., high, low), average response time of the one ormore services that participate in the processing the first portion ofthe first request, whether a remote source is needed, and/or otherfactors.

In an aspect, determining the time allocation for processing the firstportion of the first request can comprise measuring a time elapsed forprocessing the first request. For example, processing the first requestcan comprise identifying a service to process a first portion of thefirst request and any network overhead in transmitting a request toprocessing the first portion of the first request. The time forprocessing the first request can be measured. If 10 seconds has elapsedand the allocated time to process the first request is 30 seconds, thetime allocation for processing the first portion of the first requestcannot be greater than 20 seconds.

In an aspect, the time allocation can be determined via accessing arequest processing history. For example, a request processing historycan comprise a record past network transactions. In an aspect, a recordin the request processing history can represent a particular requestand/or transaction. A record can comprise information on the type of atransaction and/or service (e.g., electronic commerce transaction,electronic funds transfer transaction, etc.), whether the transactionwas successful, how long the transaction took to complete, clients andservices involved in the transaction, load on the participant clientsand services during the transaction, network condition (e.g., bandwidth,latency), network traffic during the transaction, and/or the like.

In an aspect, at least a part of the first portion of the first requestcan be processed. As an example, the first request can comprise acontent streaming request. Processing the at least a part of the firstportion of the first request can comprise encoding requested contentstreams and encapsulating the encoded content in a format suitable fordelivery. At least a part of the first portion of the first requestfirst request can be processed at the service 104 a.

It can be determined whether the processing at least the part of thefirst portion of the first request is predicted to exceed the firsttimeout parameter. For example, when processing at least the part of thefirst portion of the first request is predicted to exceed the timeallocation previously determined (e.g., 15 seconds), service 104 a canpredict the overall processing time for the first request can exceed thefirst timeout parameter (e.g., 30 seconds).

A notification indicative of exceeding the first timeout parameter canbe sent. In an aspect, the notification can be sent before the firsttimeout parameter is exceeded. For example, the notification can be sentwhen it is determined that the processing at least the part of the firstportion of the first request is predicted to exceed the first timeoutparameter. The notification can be transmitted from the service 104 a tothe client 102 before the connection between the client 102 and theservice 104 a is terminated. As an example, the notification can be asound, a code, text, a message, or the like. As an example, thenotification can be sent in the form of a custom HTTP header or field ina header.

At step 406, a second timeout parameter can be determined. For example,the second timeout parameter can be determined by one or more predefinedformula (e.g., addition, subtraction, multiplication, division, andother mathematical operations), comparison to historical information,determination of current network conditions and/or device conditions,and/or the like. For example, the second timeout parameter can bedetermined by subtracting at least the time allocation from the firsttimeout parameter. As a further example, the second timeout parametercan be determined by subtracting, from the first timeout parameter, thedetermined time allocation. In an aspect, when the service 104 aidentifies that service 104 b can process a second portion of the firstrequest. In the scenario of content streaming service, processing thesecond portion of the first request can comprise distributing processed(e.g., encoded, encapsulated) content to a content requestor (e.g.,client 102). A second timeout parameter (e.g., 10 seconds) can beassociated with the processing of the second portion of the firstrequest. In an aspect, the second timeout parameter can be determined bysubtracting at least the time allocation (e.g., 15 seconds) from thefirst timeout parameter. Other time values (e.g., one or more other timevalues) can be subtracted. As an example, the other time value can be anexpected time delay associated with overhead of processing the firstrequest. For example, the time delay can comprise time delay intransmitting the first request, determining the service to process thefirst request, determining the time allocation for processing the firstportion of the first request, determining the time allocation forprocessing the second portion of the first request, and/or the like. Thesecond timeout parameter can be determined by the service 104 a.

At step 408, a second request can be sent to perform a second portion ofthe first request. As an example, the service 104 a can send the secondrequest to the service 104 b to process the second portion of the firstrequest. The second timeout parameter (e.g., 10 seconds) can be sent tothe service 104 b along with the second request. In an aspect, thesecond portion of the first request can be processed when the secondrequest is received, for example, by the service 104 b.

In an aspect, a first notification indicative of the second requestexceeding the second timeout parameter can be received. As an example,the service 104 b can determine that the processing of the secondrequest is predicted to exceed the second timeout parameter, and theservice 104 b can generate a first notification and transmit to theservice 104 a. The first notification can be transmitted to the client102 before the connection between the service 104 a and the client(e.g., client 102) is terminated. In an aspect, the second notificationcan be determined by comparing current transaction with one or moresimilar transactions in a request processing history.

A second notification indicative of exceeding the first timeoutparameter can be sent in response to receiving the first notification.Upon receiving the first notification, the service 104 a can generate asecond notification indicative of exceeding the first timeout parameter.The first notification and/or the second notification can be transmittedto the client 102 before the connection between the service 104 a andthe client (e.g., client 102) is terminated. In an aspect, the secondnotification can be sent by comparing the current transaction with oneor more similar transactions in a request processing history.

In the event of failure, the notifications (e.g., first notification,second notification can notify a client or a service of the status(e.g., completed, not completed, failed, unable to complete withintimeout parameter) of a request (e.g., first request, second request).In another aspect, the client that initiates a service request candetermine whether to use a different timeout parameter in a subsequentrequest if a previous request is not completed within a specific timeoutparameter.

FIG. 5 is a flowchart illustrating an example method 500. At step 502, afirst request with a first timeout parameter can be sent from a firstdevice to a second device. The first request can comprise a request tocomplete a task and/or initiate a transaction (e.g., a networktransaction). The request can be received from a service, a client,device, and/or another component in the network. For example, a devicecan comprise one or more services running on the device. A client cancomprise a device requesting any type of service, such as fulfillment ofas specified task or series of tasks. As an example, the first requestcan be received from the client 102 at the service 104 a. The firsttimeout parameter (e.g., 30 seconds) can be sent from the client 102 tothe service 104 a.

In an aspect, an estimated time to complete processing the first requestcan be determined at the second device. The estimated time can bedetermined by comparing the current transaction (e.g., type of service,network conditions) with one or more similar transactions in a requestprocessing history. In another aspect, determining the estimated timecan comprise determining the number of services involved to process thefirst request and/or estimated processing time for one or more servicesto process the first request. In another aspect, determining theestimated time can comprise determining network overhead fortransmitting data associated with processing the first request among theone or more services.

In an aspect, a timeout prediction can be determined based on the firsttimeout parameter and the time estimation for processing the firstrequest. For example, the second device can make a timeout predictionthat the first timeout parameter will be exceeded. In an aspect, thesecond device (e.g., service 104 a) can be configured to fulfill thefirst request by delegating a task to a third device and/or a service,such as service 104 b. In an aspect, the task can be sent to the thirddevice and/or service (e.g., service 104 b) with a third timeoutparameter determined by the second device. The third timeout parametercan be determined by subtracting time from the first timeout parameterbased on overhead, network load, processing load, processing time, taskcomplexity, backlog, scheduled events, and/or the like. A timeoutprediction can be determined based on a respective estimated time forthe second device (e.g., service 104 b) to process the task exceeding orbeing predicted to exceed the third timeout parameter.

At step 504, a notification indicating a timeout prediction based on thefirst timeout parameter can be received at the first device from thesecond device. For example, the second device (e.g., service 104 a) canbe configured to send the notification to a client (e.g., client 102)before the first timeout parameter is exceeded. In an aspect, the seconddevice (e.g., service 104 a) can be configured to fulfill the firstrequest by delegating a task to a device and/or service, such as service104 b. In an aspect, the task can be sent to the device and/or servicewith the third timeout parameter. A notification can be sent based onthe service exceeding the third timeout parameter. In an aspect, thenotification can comprise an estimated time to complete processing thefirst request.

At step 506, a second timeout parameter can be determined, at the firstdevice, in response to receiving the notification. For example, uponreceiving the notification at step 508, the client that initiated thefirst request (e.g., client 102) can determine that the first timeoutparameter is not adequate to process the first request. For example, thesecond timeout parameter can be based on the estimated time to completeprocessing the task from the notification. The second timeout parametercan be increased from the first timeout parameter to accommodate thecurrent bandwidth, processing load, and/or the like of the seconddevice.

In an aspect, the client (e.g., client 102) can identify a third deviceor service (e.g., service 104 d) to send a second request to the seconddevice with the second timeout parameter. As an example, the thirddevice (e.g., service 104 d) can have more hardware resources (e.g.,faster processing power, less load, more memory, etc.) than the seconddevice service 104 a). The first timeout parameter can be different thanthe second timeout parameter. For example, if the third device orservice comprises a faster processor than the second device or service,the second timeout parameter can be less than the first timeoutparameter. As another example, if the third device comprises a similarprocessor compared to the second device or service, the second timeoutparameter can be greater than the first timeout parameter. In an aspect,the second timeout parameter can be determined based on one or moresimilar transactions stored in a request processing history.

At step 508, a second request can be sent (e.g., in response toreceiving the notification). For example, the second request can be sentto the identified device (e.g., third device) and/or service. The secondrequest can comprise the second timeout parameter. As another example,the second request can be sent to the second device (e.g., after sendingthe first request and receiving the notification). The second requestcan be the same as the first request with the second timeout parameterinstead of the first timeout parameter.

FIG. 6 is a block diagram illustrating an exemplary operatingenvironment for performing the disclosed methods. In an exemplaryaspect, the methods and systems of the present disclosure can beimplemented on computer 601 as illustrated in FIG. 6 and describedbelow. By way of example, one or more components shown in FIG. 2 can bea computer 601 as illustrated in FIG. 6. Similarly, the methods andsystems disclosed can utilize one or more computing devices to performone or more functions in one or more locations. This exemplary operatingenvironment is only an example of an operating environment and is notintended to suggest any limitation as to the scope of use orfunctionality of operating environment architecture. Neither should theoperating environment be interpreted as having any dependency orrequirement relating to any one or combination of components illustratedin the exemplary operating environment.

The present methods and systems can be operational with numerous othergeneral purpose or special purpose computing system environments orconfigurations. Examples of well known computing systems, environments,and/or configurations that can be suitable for use with the systems andmethods comprise, but are not limited to, personal computers, servercomputers, laptop devices, and multiprocessor systems. Additionalexamples comprise set top boxes, programmable consumer electronics,network PCs, minicomputers, mainframe computers, distributed computingenvironments that comprise any of the above systems or devices, and thelike.

The processing of the disclosed methods and systems can be performed bysoftware components. The disclosed systems and methods can be describedin the general context of computer-executable instructions, such asprogram modules, being executed by one or more computers or otherdevices. Generally, program modules comprise computer code, routines,programs, objects, components, data structures, etc. that performparticular tasks or implement particular abstract data types. Thedisclosed methods can also be practiced in grid-based and distributedcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed computing environment, program modules can be located inboth local and remote computer storage media including memory storagedevices.

Further, one skilled in the art will appreciate that the systems andmethods disclosed herein can be implemented via a general-purposecomputing device in the form of a computer 601. The components of thecomputer 601 can comprise, but are not limited to, one or moreprocessors 603, a system memory 612, and a system bus 613 that couplesvarious system components including the one or more processors 603 tothe system memory 612. In one aspect, the system can utilize parallelcomputing.

The system bus 613 represents one or more of several possible types ofbus structures, including a memory bus or memory controller, aperipheral bus, an accelerated graphics port, and a processor or localbus using any of a variety of bus architectures. By way of example, sucharchitectures can comprise an Industry Standard Architecture (ISA) bus,a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, aVideo Electronics Standards Association (VESA) local bus, an AcceleratedGraphics Port (AGP) bus, and a Peripheral Component Interconnects (PCI),a PCI-Express bus, a Personal Computer Memory Card Industry Association(PCMCIA), Universal Serial Bus (USB) and the like. The system bus 613,and all buses specified in this description can also be implemented overa wired or wireless network connection and each of the subsystems,including the one or more processors 603, a mass storage device 604, anoperating system 605, service software 606, service data 607, a networkadapter 608, system memory 612, an Input/Output Interface 610, a displayadapter 609, a display device 611, and a human machine interface 602,can be contained within one or more remote computing devices 614 a,b,cat physically separate locations, connected through buses of this form,in effect implementing a fully distributed system.

The computer 601 typically comprises a variety of computer readablemedia. Exemplary readable media can be any available media that isaccessible by the computer 601 and comprises, for example and not meantto be limiting, both volatile and non-volatile media, removable andnon-removable media. The system memory 612 comprises computer readablemedia in the form of volatile memory, such as random access memory(RAM), and/or non-volatile memory, such as read only memory (ROM). Thesystem memory 612 typically contains data, such as service data 607,and/or program modules, such as operating system 605 and servicesoftware 606, that are immediately accessible to and/or are presentlyoperated on by the one or more processors 603.

In another aspect, the computer 601 can also comprise otherremovable/non-removable, volatile/non-volatile computer storage media.By way of example, FIG. 6 illustrates a mass storage device 604 whichcan provide non-volatile storage of computer code, computer readableinstructions, data structures, program modules, and other data for thecomputer 601. For example and not meant to be limiting, a mass storagedevice 604 can be a hard disk, a removable magnetic disk, a removableoptical disk, magnetic cassettes or other magnetic storage devices,flash memory cards, CD-ROM, digital versatile disks (DVD) or otheroptical storage, random access memories (RAM), read only memories (ROM),electrically erasable programmable read-only memory (EEPROM), and thelike.

Optionally, any number of program modules can be stored on the massstorage device 604, including by way of example, an operating system 605and service software 606. Each of the operating system 605 and servicesoftware 606 (or some combination thereof) can comprise elements of theprogramming and the service software 606. Service data 607 can also bestored on the mass storage device 604. Service data 607 can be stored inany of one or more databases known in the art. Examples of suchdatabases comprise, DB2®, Microsoft® Access, Microsoft® SQL Server,Oracle®, mySQL, PostgreSQL, and the like. The databases can becentralized or distributed across multiple systems.

In another aspect, the user can enter commands and information into thecomputer 601 via an input device (not shown). Examples of such inputdevices comprise, but are not limited to, a keyboard, pointing device(e.g., a “mouse”), a microphone, a joystick, a scanner, tactile inputdevices, such as gloves, and other body coverings, and the like. Theseand other input devices can be connected to the one or more processors603 via a human machine interface 602 that is coupled to the system bus613, but can be connected by other interface and bus structures, such asa parallel port, game port, an IEEE 1394 Port (also known as a Firewireport), a serial port, or a universal serial bus (USB).

In yet another aspect, a display device 611 can also be connected to thesystem bus 613 via an interface, such as a display adapter 609. It iscontemplated that the computer 601 can have more than one displayadapter 609 and the computer 601 can have more than one display device611. For example, a display device can be a monitor, an LCD (LiquidCrystal Display), or a projector. In addition to the display device 611,other output peripheral devices can comprise components, such asspeakers (not shown) and a printer (not shown) which can be connected tothe computer 601 via Input/Output Interface 610. Any step and/or resultof the methods can be output in any form to an output device. Suchoutput can be any form of visual representation, including, but notlimited to, textual, graphical, animation, audio, tactile, and the like.The display device 611 and computer 601 can be part of one device, orseparate devices.

The computer 601 can operate in a networked environment using logicalconnections to one or more remote computing devices 614 a,b,c. By way ofexample, a remote computing device can be a personal computer, portablecomputer, smartphone, a server, a router, a network computer, a peerdevice or other common network node, and so on. Logical connectionsbetween the computer 601 and a remote computing device 614 a,b,c can bemade via a network 615, such as a local area network (LAN) and/or ageneral wide area network (WAN). Such network connections can be througha network adapter 608. A network adapter 608 can be implemented in bothwired and wireless environments. Such networking environments areconventional and commonplace in dwellings, offices, enterprise-widecomputer networks, intranets, and the Internet.

For purposes of illustration, application programs and other executableprogram components, such as the operating system 605 are illustratedherein as discrete blocks, although it is recognized that such programsand components reside at various times in different storage componentsof the computer 601, and are executed by the data processor(s) of thecomputer. An implementation of service software 606 can be stored on ortransmitted across some form of computer readable media. Any of thedisclosed methods can be performed by computer readable instructionsembodied on computer readable media. Computer readable media can be anyavailable media that can be accessed by a computer. By way of exampleand not meant to be limiting, computer readable media can comprise“computer storage media” and “communications media.” “Computer storagemedia” comprise volatile and non-volatile, removable and non-removablemedia implemented in any methods or technology for storage ofinformation, such as computer readable instructions, data structures,program modules, or other data. Exemplary computer storage mediacomprises, but is not limited to, RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disks (DVD) or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed by acomputer.

While the methods and systems have been described in connection withpreferred embodiments and specific examples, it is not intended that thescope be limited to the particular embodiments set forth, as theembodiments herein are intended in all respects to be illustrativerather than restrictive.

Unless otherwise expressly stated, it is in no way intended that anymethod set forth herein be construed as requiring that its steps beperformed in a specific order. Accordingly, where a method claim doesnot actually recite an order to be followed by its steps or it is nototherwise specifically stated in the claims or descriptions that thesteps are to be limited to a specific order, it is no way intended thatan order be inferred, in any respect. This holds for any possiblenon-express basis for interpretation, including: matters of logic withrespect to arrangement of steps or operational flow; plain meaningderived from grammatical organization or punctuation; the number or typeof embodiments described in the specification.

It will be apparent to those skilled in the art that variousmodifications and variations can be made without departing from thescope or spirit. Other embodiments will be apparent to those skilled inthe art from consideration of the specification and practice disclosedherein. It is intended that the specification and examples be consideredas exemplary only, with a true scope and spirit being indicated by thefollowing claims.

What is claimed is:
 1. A method comprising: receiving, by a computingdevice, a first computing request for a computing operation; determininga first timeout parameter associated with the first computing request;determining, by the computing device based on the first computingrequest, a first computing task for performing the computing operation;determining, before the first timeout parameter is exceeded, that apredicted processing time of the first computing task exceeds the firsttimeout parameter; determining, based on the predicted processing timeof the first computing task exceeding the first timeout parameter, asecond timeout parameter by subtracting, from the first timeoutparameter, a network overhead time; and sending, to a computing service,the second timeout parameter with a request to process the firstcomputing task.
 2. The method of claim 1, further comprising receivingthe first timeout parameter with the first computing request.
 3. Themethod of claim 1, further comprising sending, based on a determinationthat the processing of the first computing task is predicted to exceedthe second timeout parameter, a notification indicative of the firstcomputing request exceeding the first timeout parameter before the firsttimeout parameter is exceeded.
 4. The method of claim 1, wherein thesecond timeout parameter further comprises an expected time delayassociated with an overhead of a system receiving the first computingrequest.
 5. The method of claim 1, further comprising: identifying,based on at least one of the first computing task or the first computingrequest, a second computing task; and associating a third timeoutparameter with the second computing task.
 6. The method of claim 5,wherein the third timeout parameter co-terminates with the first timeoutparameter and the method further comprises: sending, based on adetermination that the second computing task exceeded or is predicted toexceed the third timeout parameter, a notification indicative ofexceeding the first timeout parameter.
 7. The method of claim 1, whereinthe network overhead time comprises a period of time required to send,to the computing service, the second timeout parameter with the requestto process the first computing task.
 8. A method comprising: receiving,by a computing device, a first computing request for a computingoperation and a first timeout parameter associated with the firstcomputing request; generating, based on a time allocation for processinga first portion of the computing operation exceeding the first timeoutparameter, a second timeout parameter by subtracting, from the firsttimeout parameter, a network overhead time; and sending a secondcomputing request to perform a second portion of the computingoperation, wherein the second computing request comprises the secondtimeout parameter.
 9. The method of claim 8, wherein the first computingrequest comprises a computing subtask of a third computing request, andwherein the first timeout parameter is based on a third timeoutparameter associated with the third computing request, wherein the thirdtimeout parameter is a time limit for processing the third computingrequest.
 10. The method of claim 8, wherein generating, based on thetime allocation for processing the first portion of the computingoperation exceeding the first timeout parameter, the second timeoutparameter further comprises subtracting, from the first timeoutparameter, a time value associated with a processing overhead associatedwith a system receiving the first computing request.
 11. The method ofclaim 8, further comprising: processing, by a computing service, a partof the first portion of the computing operation; determining that aprocessing time of processing the part of the first portion of thecomputing operation is predicted to exceed the first timeout parameter;and sending, based on the processing time being predicted to exceed thefirst timeout parameter, a notification indicative of the second timeoutparameter, wherein the notification is sent before the first timeoutparameter is exceeded.
 12. The method of claim 8, further comprising:receiving a first notification indicative of the second portion of thecomputing operation exceeding the second timeout parameter; and sending,based on receiving the first notification, a second notificationindicative of exceeding the second timeout parameter.
 13. The method ofclaim 8, wherein the time allocation for processing the first portion ofthe computing operation is determined based on a request processinghistory.
 14. The method of claim 8, further comprising processing thefirst portion of the computing operation, wherein the time allocationfor processing the first portion of the computing is based on measuringa time elapsed for processing the first computing request.
 15. A methodcomprising: sending, by a first computing device to a second computingdevice, a first computing request for a computing operation thatcomprises a first timeout parameter; receiving, by the first computingdevice, a notification indicating a timeout prediction, wherein thefirst computing device receives the notification before the firsttimeout parameter is exceeded; determining, by the first computingdevice based on the notification, a second timeout parameter bysubtracting, from the first timeout parameter, a network overhead time;and sending a second computing request comprising the second timeoutparameter.
 16. The method of claim 15, further comprising: generating,by the second computing device based on the first timeout parameter, athird timeout parameter, wherein the second computing device isconfigured to fulfill the first computing request by delegating acomputing task for completing the computing operation to a computingservice, wherein the computing task is sent to the computing servicewith the third timeout parameter.
 17. The method of claim 16, whereingenerating, by the second computing device based on the first timeoutparameter, the third timeout parameter comprises subtracting a timevalue from the first timeout parameter, wherein the time value is basedon a processing overhead associated with the second computing device.18. The method of claim 16, further comprising: sending, by the secondcomputing device to the first computing device based on the computingservice exceeding the third timeout parameter, the notificationindicating the timeout prediction.
 19. The method of claim 15, furthercomprising sending the second computing request to a third computingdevice.
 20. The method of claim 15, further comprising: receiving, bythe first computing device, a notification indicating the secondcomputing request is predicted to exceed the second timeout parameterbefore the second timeout parameter is exceeded.